disable HDF5 file locking #2314
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There has been an error in gunicorn logs coming from the tool predictions API:
From a google search I found recommendations to use
HDF5_USE_FILE_LOCKING: "FALSE". Checked out EU and Main infrastructure playbooks and found that they are already using this, and they have adopted it recently. (galaxyproject/usegalaxy-playbook@3724a13#diff-68bca5ccf2e9695dcca9925b36cce7bb8e7bd223d9c6531649be01986c661020R31)I'm not sure if this means instances are individually compensating for something that has gone wrong in Galaxy